[tolerant,stretch]
\setupfirstline
[alternative=line,
color=darkred,
style=\setfontfeature{smallcaps}]
\setupfirstline
[fancy]
[n=3]
\setupfirstline
[fancier]
[alternative=word,
color=darkblue,
style=bold,
n=3]
\setupfirstline
[weirder]
[alternative=line,
color
(emboldened, italicized).
\definefirstline[SC][alternative=line,style=\setfontfeature{smallcaps}]%
or =\sc
\definefirstline[BD][alternative=line,style=bold]
\definefirstline[IT][alternative=line,style=italic]
\setupbodyfont[termes,11pt]% requires font with small caps
).
\definefirstline[SC][alternative=line,style=\setfontfeature{smallcaps}]%
or =\sc
\definefirstline[BD][alternative=line,style=bold]
\definefirstline[IT][alternative=line,style=italic]
\setupbodyfont[termes,11pt]% requires font with small caps
\starttext
\setfirstline[SC
] \Setupbodyfont{\setupbodyfont[#1,11pt]}
\define[1] \DisplayExample{\switchtobodyfont[#1]\getbuffer}
\setupfirstline [alternative=line,
style=\setfontfeature{smallcaps}]
\setupinitial [location=text,n=2,color=darkred]
\setuphead [chapter
=\setfontfeature{smallcaps}]
\setfirstline[fancy] \input tufte \par
\setfirstline[fancy] \input ward \par
\setfirstline[fancy] \input knuth \par
\setfirstline[fancy] \input bryson \page
\definefirstline
[fancy]
[alternative=word,
color=darkblue
few words) for instance in smallcaps.
Another curiosity question: is it on purpose that
\definefirstline
[fancy]
[alternative=line,
color=darkred,
style=\setfontfeature{smallcaps},
n=2]
does not produce two lines of text in smallcaps?
Best regards: OK
On 22
,
color=darkred,
style=\setfontfeature{smallcaps}]
\setupfirstline
[fancy]
[n=3]
\setupfirstline
[fancier]
[alternative=word,
color=darkblue,
style=bold,
n=3]
\setupfirstline
[weirder]
[alternative=line,
color=darkgreen,
style=\setfontfeature{smallcaps},
n=3
Hi,
Some new magic in the beta ...
\setupbodyfont[pagella]
\starttext
\setupindenting[medium,yes]
\setupalign[tolerant]
\definefirstline
[fancy]
[alternative=line,
color=darkred,
style=\setfontfeature{smallcaps}]
\setfirstline[fancy] \input tufte
=myfeatures]
Sometimes it is necessary to add additional features or to switch a different
feature list *in* the document. To do this context provides the commands
\addfontfeature and \setfontfeature which can be also called in the two shorter
commands \addff and \setff. In the \definehighlight
\addfontfeature and \setfontfeature which can be also
called in the two shorter commands \addff and \setff. In the
\definehighlight command I enabled the predefined “none” list where
ligatures and kerning is disabled to prevent that -- results in –.
Wolfgang
to \setfontfeature?
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma
-optical]
\usetypescript
[minion]
\setupbodyfont
[minion]
\setupnote
[footnote]
[textcommand=\setfontfeature{superscripts},
textstyle=,
numbercommand=]
\starttext
\dorecurse{9}{This\footnote{Hello World #1} is a test.\par }
\stoptext
---
The problem
Consider the following example
\definefontfeature[capital spacing] [cpsp=yes]
\definefontfeature[small capitals] [c2sc=yes]
\starttext
\setfontfeature{capital spacing} % not OK
% \setfontfeature{small capitals} % OK
ABCDEFGHIJKLMNOPQRSTUVWXYZ
\stoptext
It works okay with small capitals
[default][liga=yes,kern=yes,tlig=yes,trep=yes,mode=node]
You can add a feature with this:
\definefontfeature[default][default][mode=node]
\definefontfeature[notrep][liga=yes,kern=yes,tlig=yes,trep=no,mode=node]
\def\realquotesingle{{\setfontfeature{notrep}'}}
Another option is to disable only
]
\definefontfeature[notrep][liga=yes,kern=yes,tlig=yes,trep=no,mode=node]
\def\realquotesingle{{\setfontfeature{notrep}'}}
\starttext
Straight quote: \realquotesingle
Standard quote: '
\stoptext
Will wikify later today in case anyone else ever needs this.
Pont
Macros
\def\orn{\setfontfeature{ornaments}}
\def\itsw{\setfontfeature{swash}\it}
\def\sw{\setfontfeature{swash}}
\def\smcp{\setfontfeature{smallcaps}}
\def\lnfigures{\setfontfeature{lining}}
\def\tabfigures{\addfontfeaturetofont{tabular}}
\def\lntabfigures{\setfontfeature{tabular}}
Wolfgang
, the documents compiles.
Change these defintions from \def to \unexpanded\def
% Font Features Macros
\def\orn{\setfontfeature{ornaments}}
\def\itsw{\setfontfeature{swash}\it}
\def\sw{\setfontfeature{swash}}
\def\smcp{\setfontfeature{smallcaps}}
\def\lnfigures{\setfontfeature{lining}}
\def
Hi all,
I have some setups like:
\setupfootnotes[textstyle=\plf] or
\setupitemize[style=\plf] where \plf is defined as:
\definefontfeature[plf][default] [pnum=yes,lnum=yes]
\def\plf{\groupedcommand{\setfontfeature{plf}}{}}
With the newest beta this setup fails. For footnotes one can use
Am 21.01.2011 um 11:38 schrieb Andreas Harder:
Hi all,
I have some setups like:
\setupfootnotes[textstyle=\plf] or
\setupitemize[style=\plf] where \plf is defined as:
\definefontfeature[plf][default] [pnum=yes,lnum=yes]
\def\plf{\groupedcommand{\setfontfeature{plf
Am 21.01.2011 um 14:48 schrieb Wolfgang Schuster:
\definefontfeature[default] [default] [mode=node,onum=yes]
\definefontfeature[plf] [default] [pnum=yes,lnum=yes]
\definefontfeature[tlf] [default] [tnum=yes,lnum=yes]
\def\plf{\groupedcommand{\setfontfeature{plf}}{}}
\def\tlf
Hi all,
please have a look at my example:
\definefontfeature[default][default][mode=node,onum=yes]
\definefontfeature[sc][default][smcp=yes]
\def\sc{\groupedcommand{\setfontfeature{sc}}{}}
\setupbodyfont[palatino]
\starttext
\startTEXpage[offset=1ex]
{\sc Abc} 0369 \crlf
\sc{Abc} 0369
On 13/10/10 12:48, Andreas Harder wrote:
Hi all,
please have a look at my example:
\definefontfeature[default][default][mode=node,onum=yes]
\definefontfeature[sc][default][smcp=yes]
\def\sc{\groupedcommand{\setfontfeature{sc}}{}}
\setupbodyfont[palatino]
\starttext
\startTEXpage[offset=1ex
On 13-10-2010 12:48, Andreas Harder wrote:
It seems that if a line starts with \sc{…} the onum-option is ignored. Is there
a solution?
fixed in upcoming beta
-
Hans Hagen | PRAGMA ADE
Am 13.10.2010 um 14:40 schrieb Hans Hagen:
On 13-10-2010 12:48, Andreas Harder wrote:
It seems that if a line starts with \sc{…} the onum-option is ignored. Is
there a solution?
fixed in upcoming beta
Thanks Hans!
Andreas
in exactly this particular context.
A nice trick i found in the core (typo-cap.mkiv)
\def\sc{\setfontfeature{smallcaps}} % \addff{smallcaps}?
\definefontfeature [default] [default] [mode=node,onum=yes]
\definefontfeature [smallcaps] [default] [smcp=yes]
\setupenumerations[footnote][before=\char\zerocount
Hi again,
footnotes keep me busy:
···8··
\def\sc{\setfontfeature{smallcaps}}
\definefontfeature [default][default]
[mode=node,onum=yes,liga=yes]
\definefontfeature [smallcaps][default]
[mode=node,onum=yes,smcp
\subtractfontfeaturefromset {..} % merge
\addfontfeaturetofont {..} % overload
\subtractfontfeaturefromfont{..} % overload
\let\addfs\addfontfeaturetoset
\let\subfs\subtractfontfeaturefromset
\let\addff\addfontfeaturetofont
\let\subff\subtractfontfeaturefromfont
there's also \setfontfeature
[SerifBold] [name:GaramondPremrPro-Smbd]
[features=default]
\definefontsynonym [SerifBoldItalic] [name:GaramondPremrPro-SmbdIt]
[features=default]
\stoptypescript
\def\sc{\setfontfeature{smallcaps}}
\def\os{\setfontfeature{oldstyle}}
\definefontfeature [default][default
][color=blue]
\starttext
{\setfontfeature[blue]Blue text}
gives the same result as
\color[blue]{blue text}
\stoptext
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki
line should disable ligatures in small caps altogether.
\definefontfeature[smallcaps][smallcaps][liga=no]
Did it work with this redefinition of the smallcaps feature?
\definefontfeature[smallcaps][smallcaps][mode=node]
With \setfontfeature{oldstyle}, I don't seem to get any small caps
about these things), and also because the
second
line should disable ligatures in small caps altogether.
\definefontfeature[smallcaps][smallcaps][liga=no]
Did it work with this redefinition of the smallcaps feature?
\definefontfeature[smallcaps][smallcaps][mode=node]
With \setfontfeature
Mika Ritola wrote:
I have to reply to my own mail because I just updated simplefonts and
noticed that the latest version behaves a bit differently. The
[oldstylefigures=yes] option still works perfectly, but now both
\setfontfeature{oldstyle} and \addfontfeaturetoset{oldstyle} result in small
Am 24.09.2009 um 14:24 schrieb Hans Hagen:
Mika Ritola wrote:
I have to reply to my own mail because I just updated simplefonts and
noticed that the latest version behaves a bit differently. The
[oldstylefigures=yes] option still works perfectly, but now both
\setfontfeature{oldstyle
still works perfectly, but now both
\setfontfeature{oldstyle} and \addfontfeaturetoset{oldstyle} result in
small
caps not working at all.
that's for Wolfgang to sort out then (that is: the interaction betweem his
settings and dynamic features)
there is one method to get oldstyle figures
.
\definefontfeature[smallcaps][smallcaps][liga=no]
Did it work with this redefinition of the smallcaps feature?
\definefontfeature[smallcaps][smallcaps][mode=node]
With \setfontfeature{oldstyle}, I don't seem to get any small caps at all in
node mode. If I replace it with the line that you
altogether.
\definefontfeature[smallcaps][smallcaps][liga=no]
Did it work with this redefinition of the smallcaps feature?
\definefontfeature[smallcaps][smallcaps][mode=node]
With \setfontfeature{oldstyle}, I don't seem to get any small caps at all in
node mode. If I replace it with the line
old-style figures should affect ligatures at all (not that I
know anything about these things), and also because the second line should
disable ligatures in small caps altogether.
\usemodule[simplefonts]
\definefontfeature[smallcaps][smallcaps][liga=no]
\setfontfeature{oldstyle}
\setmainfont[Adobe
it work with this redefinition of the smallcaps feature?
\definefontfeature[smallcaps][smallcaps][mode=node]
\setfontfeature{oldstyle}
\setmainfont[Adobe Jenson Pro]
\setmainfont[Adobe Jenson Pro][oldstylefigures=yes]
Wolfgang
?
Another way is to use the 'frac' feature.
\definefontfeature[frac][default][script=latn,frac=yes]
\definefont[minion][name:minionproregular*default]
\def\utffrac{\groupedcommand{\setfontfeature{frac}}{}}
\starttext
\minion 1/2 \utffrac{1/2} 1/2 \utffrac{12345/6789} 12345/6789
\stoptext
][AdobeSongStd-Light][features=zh]
\definefont[ChineseFont][zhserif at 12pt]
however, in experimental version, it will report zhserif not found.
So I can only write something like:
\definefont[ChineseFont][AdobeSongStd-Light*zh at 12pt]
Bug or feature?
btw, I can use setfontfeature, how can I unset a font
a...
?
%%% test.tex %%%
% engine=luatex
\enableregime [utf-8]
\def\sc{\setfontfeature{smallcaps}}
\definefontfeature
[default][default]
[protrusion=quality,expansion=quality,mode=node,script=latn]
\definefontfeature
[oldstyle][default]
[protrusion=quality,expansion=quality,mode=node
=latin-smallcaps]
\stoptypescript
%%% Then i've got this in the file i want to typeset %%%
\def\sc{\setfontfeature{smallcaps}}
\definefontfeature
[default][default]
[protrusion=quality,expansion=quality,mode=node,script=latn]
\definefontfeature
[oldstyle][default]
[protrusion
On Sun, Nov 23, 2008 at 7:12 AM, Yue Wang [EMAIL PROTECTED] wrote:
Hi,
3. In a many OpenType fonts you could get small caps with
the smcp feature, to use it redefine the \sc command to
\def\sc{\groupedcommand{\setfontfeature{smallcaps}}{}}.
I can enable a feature using
caps with
the smcp feature, to use it redefine the \sc command to
\def\sc{\groupedcommand{\setfontfeature{smallcaps}}{}}.
Wolfgang
___
If your question is of interest to others as well, please add an entry
Hi,
3. In a many OpenType fonts you could get small caps with
the smcp feature, to use it redefine the \sc command to
\def\sc{\groupedcommand{\setfontfeature{smallcaps}}{}}.
I can enable a feature using the \setfontfeature, how can I disable a feature?
like \setfontfeature{-smcp}?
btw
in any font (gyre fonts doesn't have that yet?)
\usetypescript[palatino]
\setupbodyfont[palatino]
\def\os{\groupedcommand{\setfontfeature{oldstyle}}{}}
\starttext
0123456789 {\os 0123456789}
\stoptext
Test the other fonts by yourself.
2. adventor have italic but slanted displays as normal
of problems I've encountered:
1. No small-caps in any font (gyre fonts doesn't have that yet?)
\usetypescript[palatino]
\setupbodyfont[palatino]
\def\os{\groupedcommand{\setfontfeature{oldstyle}}{}}
Shouldn't that be just
\def\os{\setufontfeature{oldstyle}}
Aditya
\starttext
0123456789 {\os
TeX Gyre fonts work with as few definitions as possible. Here is the
list
of problems I've encountered:
1. No small-caps in any font (gyre fonts doesn't have that yet?)
\usetypescript[palatino]
\setupbodyfont[palatino]
\def\os{\groupedcommand{\setfontfeature{oldstyle}}{}}
Shouldn't
as possible. Here is
the list
of problems I've encountered:
1. No small-caps in any font (gyre fonts doesn't have that yet?)
\usetypescript[palatino]
\setupbodyfont[palatino]
\def\os{\groupedcommand{\setfontfeature{oldstyle}}{}}
Shouldn't that be just
\def\os{\setufontfeature{oldstyle
\os to something
\def\os{\groupedcommand{\setfontfeature{oldstyle}}{}}
which in mkiv will make
1234567890 {\os 1234567890} 1234567890
work
___
If your question is of interest to others as well, please add
Wolfgang Schuster wrote:
Am 01.10.2008 um 00:08 schrieb Hans Hagen:
Wolfgang Schuster wrote:
Hi Hans,
Japanese text is no longer broken across lines, it works only
if I set the right feature with \setfontfeature but settings given
with feature=... in \definefontsynonym are ignored.
ok
Am 01.10.2008 um 11:22 schrieb Hans Hagen:
Wolfgang Schuster wrote:
Am 01.10.2008 um 00:08 schrieb Hans Hagen:
Wolfgang Schuster wrote:
Hi Hans,
Japanese text is no longer broken across lines, it works only
if I set the right feature with \setfontfeature but settings given
with feature
is kind of special because it's related to the fact that good old
tex and the cm fonts have oldstyles in some math font and therefore some
effort is needed to use it in text
we might consider mapping \os to something
\def\os{\groupedcommand{\setfontfeature{oldstyle}}{}}
which in mkiv will make
, cap=round] (-7.65cm,-1mm) --
(7.65cm,-1mm);
\stoptikzpicture
\stoptext
When I compile my document with texexec --lua I get a black line.
Adding \setfontfeature{oldstyle} to the preamble causes texexec
--lua to break with a failure.
Package pgfbase: Error! Unsupported color model `'. Sorry
even adapt features in between if needed (dynamic features)
How to use dynamic features? it is not documented in co-typography and
co-fonts.
is there such interface like:
\definefeature[onum][onum=yes]
\definefeature[smcp][smcp=yes]
\def\onum{\setfontfeature{onum}}
{\rm\bf\onum\smcp Hello
Hi,
I cannot copy oldstyle numbers from a pdf. Consider
\usetypescript[palatino]
\setupbodyfont[palatin,12pt]
\setfontfeature{oldstyle}
\starttext
12345
\stoptext
When I copy from pdf (or run pdftotext) I get
How do I correct
] [delicious] [default] [features=default,
rscale=1.1]
\definetypeface [mainface] [tt] [mono] [modern] [default] [features=default,
rscale=1.1]
\definetypeface [mainface] [mm] [math] [palatino] [default] [encoding=texnansi]
\setupbodyfont[mainface,12pt]
\setfontfeature{oldstyle}
\setuppapersize [letter
\def\sc{\setfontfeature{smallcaps}}
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage
Hi,
Something is wrong with palatino smallcaps and oldstyle. The attached
image shows the output of the following test file.
\usetypescript[palatino]
\setupbodyfont[palatino]
\setfontfeature{oldstyle}
\starttext
Definition
\smallcaps{Definition}
\stoptext
Adityaattachment
=dflt,liga=yes,onum=yes,kern=yes]
\usetypescriptfile[seravek]
\usetypescript[Seravek]
\setupbodyfont[Seravek,12pt]
% \def\sc{\setfontfeature{smcp}}
% \def\os{\setfontfeature{onum}}
\starttext
Hello World! {\sc ABC abc} {\os 123} 1 2 3 4 5 6 7 8 9
\blank
{\sc Hello World!}
\blank
{\bf Hello World
,script=latn,language=dflt,liga=yes,onum=yes,kern=yes]
\usetypescriptfile[seravek]
\usetypescript[Seravek]
\setupbodyfont[Seravek,12pt]
% \def\sc{\setfontfeature{smcp}}
% \def\os{\setfontfeature{onum}}
\def\sc{\setfontfeature{smallcaps}}
\def\os{\setfontfeature{oldstyle}}
or
\def\sc
[seravek]
\usetypescript[Seravek]
\setupbodyfont[Seravek,12pt]
% \def\sc{\setfontfeature{smcp}}
% \def\os{\setfontfeature{onum}}
\def\sc{\setfontfeature{smallcaps}}
\def\os{\setfontfeature{oldstyle}}
or
\def\sc{\setfontfeature{smallcaps}}
\def\os{\setfontfeature{OldstyleFigures
]
\definetypeface [constantia] [ss] [sans] [candara] [default]
\setupbodyfont[constantia,11pt]
This is my test file:
\usetypefile [vista]
\usetypescript[candara]
\setupbodyfont[candara]
\def\sc{\setfontfeature{latin-smallcaps}}
\def\os{\setfontfeature{latin-oldstyle}}
\starttext
\ss Text Va ffi ffi
Aditya Mahajan wrote:
Hi,
While using oldstyle features with mkiv, -- in a typing environment comes
out as a endash. I would consider this a bug.
For example:
\setfontfeature{oldstyle}
\starttext
\starttyping
-- A comment 123
\stoptyping
\stoptext
Another interesting feature
Hi,
While using oldstyle features with mkiv, -- in a typing environment comes
out as a endash. I would consider this a bug.
For example:
\setfontfeature{oldstyle}
\starttext
\starttyping
-- A comment 123
\stoptyping
\stoptext
Another interesting feature is that numbers in the typing
things like this using \setfontfeature or something
similar. Hans will know for sure (but he at bachotex right now)
I wrote a simpler example and compiled it with my old and my current ConTeXt.
http://schuster.wolfgang.googlepages.com/files - Fontfeature
Greetings
Wolfgang
stable online.
http://schuster.wolfgang.googlepages.com/files
IIRC, \Var depends on a very particular way of writing typescripts,
and is currently considered deprecated by Hans, and that there is a
new way to do things like this using \setfontfeature or something
similar. Hans will know for sure
things like this using \setfontfeature or something
similar. Hans will know for sure (but he at bachotex right now)
This did also happen with [feature=...] in typescripts or with \setfontfeature
in a document. A few fonts like Pagella or Linux Libertine work as expected
but Cambria is a example where
- oldstyle
It is also possible to change the features of a font within the text
with the command \setfontfeature{...}.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki
trying to do right now.
ConTeXt has the following features predefined:
- default
- smallcaps
- oldstyle
Yep, I saw them in font-ini.tex, as you pointed me to.
It is also possible to change the features of a font within the text
with the command \setfontfeature{...}.
But, if I've understood
font features with \definefontfeature
It is also possible to change the features of a font within the text
with the command \setfontfeature{...}.
But, if I've understood the point, there is no reason to do that if I
use a proper typescript. Right?
It depends what do you want, normally
==
% engine=luatex
\definefontfeature
[oldstyle]
[mode=node,language=dflt,script=latn,onum=yes,tnum=yes]
\setfontfeature{oldstyle}
\starttext
1234567890
\stoptext
==
Best wishes
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
]
\setfontfeature{oldstyle}
\starttext
1234567890
\startitemize
\item test
\stopitemize
\stoptext
==
log:
error: ...onTeXt/tex/texmf-local/tex/context/base/font-otf.lua:1890:
attempt to index local 'shared' (a nil value)
.
\dolistitem
,tnum=yes]
\setfontfeature{oldstyle}
\starttext
1234567890
\startitemize
\item test
\stopitemize
\stoptext
==
in font=otf.lua, patch ...
function fonts.otf.set_dynamics(tfmdata,attribute,features)
local shared = tfmdata.shared
want to achieve, local changes can be done with
\os, but this will use numbers from the math font.
That's exactly why \os is almost useless (it messes up itemizations and
other stuff); better to \switchtotypeface, even for local changes.
option two is to write
\setfontfeature{oldstyle
\definefontfeature
[oldstyle]
[mode=node,language=dflt,script=latn,onum=yes,tnum=yes]
\setfontfeature{oldstyle}
\starttext
1234567890
\startitemize
\item test
\stopitemize
\stoptext
==
in font=otf.lua, patch ...
function
Wolfgang Schuster wrote:
you forgot local dynamics, the following works
function fonts.otf.set_dynamics(tfmdata,attribute,features)
local shared = tfmdata.shared
local dynamics = shared.dynamics
if shared then
hm, you need to to test shared before using it, so
not ;-)
==
% engine=luatex
\setfontfeature{oldstyle}
\starttext
test
1234567890
\stoptext
==
There is currently no better way to enable oldstyle number for the
whole document except you define your own typescripts and use
On Wed, 02 Jan 2008 02:11:22 -0700, Hans Hagen [EMAIL PROTECTED] wrote:
in font=otf.lua, patch ...
function fonts.otf.set_dynamics(tfmdata,attribute,features)
local shared = tfmdata.shared
if shared then
end
end
and remake
Does this handle the other
On Wed, 02 Jan 2008 08:14:17 -0700, Taco Hoekwater [EMAIL PROTECTED]
wrote:
Does this handle the other [off-list] utf-8 bug that generates an error
message from font-tfm.lua:591?
No. You get that error because the font does not have a non-breaking
hyphen, and you can fix it by changing
the math font.
Mark IV has a new the new option fontfeatures and you can use this
to get the oldstyle numbers from the latin modern OT fonts. Option one
is to redefine \os to use the numbers from the main font, you have to
put the following command in your document,
\def\os{\setfontfeature{oldstyle
On Jan 2, 2008 4:19 AM, Idris Samawi Hamid [EMAIL PROTECTED] wrote:
Dear consortium,
check this out:
==
% engine=luatex
\definefontfeature
[oldstyle]
[mode=node,language=dflt,script=latn,onum=yes,tnum=yes]
\setfontfeature{oldstyle
be considered as a theoretical
possibility, it is needed quite often.
Steffen
The following should work, can't test it at the moment
\definefontfeature[enableoldstyle][onum=yes]
\definefontfeature[disableoldstyle][onum=no]
\starttext
123 \setfontfeature{enableoldstyle} 456 \setfontfeature
=no]
\starttext
123 \setfontfeature{enableoldstyle} 456 \setfontfeature{disableoldstyle}
789
\stoptext
btw, these are attributes and therefore can be used grouped
123 {\setfontfeature{enableoldstyle} 456} 789
Is it also possible to inherit the values from the previuos change,
e.g. I
the fonfeatures define in the typescript
\setupbodyfont[myfont][features=oldstyle] choose oldstyle figures instead
of the default setting in the typescript, this requires at the moment always
a second typescript with oldstyle numerals.
It would also nice to map \sc to \setfontfeature{smallcaps} because
it at the moment
\definefontfeature[enableoldstyle][onum=yes]
\definefontfeature[disableoldstyle][onum=no]
\starttext
123 \setfontfeature{enableoldstyle} 456 \setfontfeature{disableoldstyle} 789
\stoptext
Wolfgang
.
Steffen
The following should work, can't test it at the moment
\definefontfeature[enableoldstyle][onum=yes]
\definefontfeature[disableoldstyle][onum=no]
\starttext
123 \setfontfeature{enableoldstyle} 456 \setfontfeature
{disableoldstyle} 789
\stoptext
you mean typeset with Lua
be considered as a theoretical
possibility, it is needed quite often.
Steffen
The following should work, can't test it at the moment
\definefontfeature[enableoldstyle][onum=yes]
\definefontfeature[disableoldstyle][onum=no]
\starttext
123 \setfontfeature{enableoldstyle} 456
something like that ...
keep in mind that you don't need to define a font then,
{\setfontfeature{smallcaps}Some Text}
will automatically give you that featureset so in practice we can do
with only a few real font definitions; mkiv keeps track of such dunamic
features and efficiently caches data;
we
be considered as a theoretical
possibility, it is needed quite often.
Steffen
The following should work, can't test it at the moment
\definefontfeature[enableoldstyle][onum=yes]
\definefontfeature[disableoldstyle][onum=no]
\starttext
123 \setfontfeature{enableoldstyle} 456 \setfontfeature
Am 06.12.2007 um 18:55 schrieb Hans Hagen:
something like that ...
keep in mind that you don't need to define a font then,
{\setfontfeature{smallcaps}Some Text}
will automatically give you that featureset so in practice we can do
with only a few real font definitions; mkiv keeps track
Steffen Wolfrum wrote:
Am 06.12.2007 um 18:55 schrieb Hans Hagen:
something like that ...
keep in mind that you don't need to define a font then,
{\setfontfeature{smallcaps}Some Text}
will automatically give you that featureset so in practice we can do
with only a few real font
{\setfontfeature{chinese} MORE BLA} bla bla
{\setfontfeature{oldstyle} 1234} bla bla
\stoptext
so, just one font instance and independent feature switches; this saves
multiple definitions of fonts and is therefore faster and takes less
memory too
Hans
93 matches
Mail list logo
